Enterprise architecture repositories and collaboration https://t.co/6U6cgGJ0n3 #entarch
http://twitter.com/jfdeclercq_biz/status/781535517099823104

ArchiMate 3.0 metamodel PDF | Mastering ArchiMate https://t.co/JwNjqhvhBH #entarch
http://twitter.com/jfdeclercq_biz/status/781515175597932548

I just wanted to draw your attention to a SCRUM/KANBAN/XP acronym : INVEST.

INVEST represents the the characteristics of a good quality Product Backlog Item (PBI) :

• Independent
• Negotiable
• Valuable
• Estimatable
• Small
• Testable

See INVEST on Wikipedia

Sounds a bit like a SMART objective……

Wilmots critique l'UB avant d'avoir touché. Deschacht parie sur ses propres matches. Les footballeurs ne sont que des footballeurs... #foot
http://twitter.com/jfdeclercq/status/781080817065979904

Wilmots critique l'UB avant d'avoir touché. Deschacht parie sur ses propres matches. Les footballeurs ne sont que des footballeurs... #foot

I also feel that way: Why young people don't buy cars and apartments anymore https://t.co/ffgvZda1KS
http://twitter.com/jfdeclercq/status/780509249126498304

I also feel that way: Why young people don't buy cars and apartments anymore http://ift.tt/2dn0X1k

Real connection

RT @jfdeclercq_biz: Strategies for your enterprise architecture: people or documentation ? | https://t.co/m00T83K9qI #entarch #strategy
http://twitter.com/appepaper/status/780078491945623552

RT @SamuelEtienne: On a retrouvé le bébé de l'album Nevermind de Nirvana :) https://t.co/k2dN4zI8xH
http://twitter.com/jfdeclercq/status/780079731907629056

Strategies for your enterprise architecture: people or documentation ? | https://t.co/XnFY4spHGF https://t.co/DPA62FXvT9 #strategy
http://twitter.com/jfdeclercq_biz/status/780072453141852160

Here is an interesting thought of a colleague yesterday (Thomas Vermassen – Lead Architect ORES) on documenting IT systems:

You have basically two strategies for keeping your Enterprise Architecture knowledge under control.

The first one is to capitalize on people. If your organization is stable enough you can assign clear responsibilities and you should be able to find the right information by finding the right person.

The second one is to capitalize on documentation. Through deliverables you make sure everything is described as it should be. This is most suitable if you have a high collaborators turnover like when you work with a lot of sub-contractors.

The ideal world is probably to have both.

I’m a deliverable minded person and I so I tend to prefer the second one. I value information sharing as it often avoids job protection and silo thinking. The notion of deliverable is also linked to another value that I like : personal contribution.

Also when the architecture is complex I don’t see how you can just book a meeting with someone in oder for him to explain you the 100 business processes in scope. That must be why clever people write books……

---

Watch "The discipline of Business Architecture" on YouTube https://t.co/q44bczNRXI #entarch
http://twitter.com/jfdeclercq_biz/status/779395229648621569

What does our society need ? World Peace of course. Watch "Miss Congeniality - World Peace" on YouTube https://t.co/n6BVYwa8Et
http://twitter.com/jfdeclercq/status/778568765017624577

What does our society need ? World Peace of course. Watch "Miss Congeniality - World Peace" on YouTube http://ift.tt/2cCFAYX

Goal de Thomas Declercq. Grez revient à 1-2 (si j'ai pas loupé un goal)

Parmi les attitudes qu'on rencontre au boulot et ailleurs: un mec en basquettes monte dans une formule1.... https://t.co/WV3rbvuPyD
http://twitter.com/jfdeclercq_biz/status/776714104128102400